• error writing /etc/modprobe.d/alsa-base.conf

    Help and Support
    3
    0 Votes
    3 Posts
    1k Views
    D

    **
    hey mitu, finaly got it working!
    But now i noticed the snes sounds are stille crackling,
    Am i missing something?**

    Followd this guide:
    link text

    Guide from link:

    Ok, first delete the file /etc/modprobe.d/alsa-base.conf Raspbian Jessie does not use this config file like Wheezy did.

    To find what address your device uses you need to first enter the command aplay -l this shows all audio output devices, and their address. For example, my USB sound card comes up as device 1 in the output which looks like this.

    card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
    Subdevices: 8/8
    Subdevice #0: subdevice #0
    Subdevice #1: subdevice #1
    Subdevice #2: subdevice #2
    Subdevice #3: subdevice #3
    Subdevice #4: subdevice #4
    Subdevice #5: subdevice #5
    Subdevice #6: subdevice #6
    Subdevice #7: subdevice #7
    card 1: Device [USB PnP Sound Device], device 0: USB Audio [USB Audio]
    Subdevices: 0/1
    Subdevice #0: subdevice #0
    Now, to set the device to your default card you will need to edit the file /usr/share/alsa/alsa.conf with the command sudo nano /usr/share/alsa/alsa.conf scroll down until you find the lines

    defaults.ctl.card 0
    defaults.pcm.card 0
    and change them to (if your device is also listed as device 1, if not change the 1 to whatever address it was listed at)

    defaults.ctl.card 1
    defaults.pcm.card 1
    Explanation: USB sound cards are registered as card 1 on Raspbian Jessie. On Wheezy they would be registered as card -2 by default and editing /etc/modprobe.d/alsa-base.conf would change that.

    I do not know if this next step is necessary but without it my card wouldn't work.

    Create and edit the file ~/.asoundrc by using the command sudo nano ~/.asoundrc and change it so that it only reads this:

    pcm.!default {
    type hw
    card 1
    }

    ctl.!default {
    type hw
    card 1
    }
    Now your default audio out (speakers) and audio in (mic) are your usb device.

  • Rpi USB audio woes and other zombies.

    Help and Support
    55
    0 Votes
    55 Posts
    14k Views
    HexH

    I am online let me know.

  • Mame & usb sound

    Help and Support
    2
    0 Votes
    2 Posts
    614 Views
    rbakerR

    @Atomize It's impossible to assist without the information requested in:
    https://retropie.org.uk/forum/topic/3/read-this-first

  • 1 Votes
    3 Posts
    1k Views
    HexH

    @Finndersen The feature is already implemented in latest ES. In Sound Settings change audio device to "Speaker" and omx audio device try both ALSA options to see which works. Let me know how it goes.

  • USB Sound Card No Video Preview Audio

    Help and Support
    3
    0 Votes
    3 Posts
    993 Views
  • 0 Votes
    4 Posts
    1k Views
    rigR

    @BuZz said in usb audio and mame4all incompatibility ?:

    @rig if you have a rpi3, you will find lr-mame2003 a better emulator.

    Yea, I have lr-mame2003 but I don't use it as much. when I first started using mame I played a few roms on both emulators and came to the conclusion that mame4all worked better. By "worked better" I mean that the sound was cleaner/clearer on a few games and the video resoulution looked sharper on a few games. However I have run into exceptions-- I use lr-mame-2003 for St Dragon because it sounds much better compared to mame4all; I also play x-men on lr-mame 2003 becsuse the sprite shadows look better.
    I didn't run a thorough test and I could be mistaken. Maybe I should give lr-mame2003 another go. What do you mean specifically by lr-mame2003 being a better emulator?
    I can say that I do prefer lr-mame4all over mame4all because of the retroarch support.

    p.s. I am using a rpi3

  • USB and HDMI audio help

    Help and Support
    1
    0 Votes
    1 Posts
    541 Views
    No one has replied
  • 0 Votes
    9 Posts
    2k Views
    mituM

    If you're still using mame4all, then I don't think there's a solution - it's a known problem and since there's no new development is happening for this emulator, it's unlikely it got fixed. I think there was a recent topic with the same symptoms for the latest RetroPie version.

    Otherwise, please open a new topic instead of bumping a 3 years old topic, and add some info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

  • 0 Votes
    6 Posts
    6k Views
    B

    Update
    I'm glad you got it working!

    @VladoPortos said in USB Audio dongle have no sound in emulators.:

    I personally thinks maybe its something with retroarch, I'm trying now specify correct HW in /opt/retropie/configs/all/retroarch.cfg under audio_device = , but so far no luck :(

    I agree, it sounds like it's just the RetroArch emulators without sound. I also think it might be a setting in /opt/retropie/configs/all/retroarch.cfg

    RetroPie comes with a backup of their custom all retroarch.cfg with default settings. It is located here:
    /opt/retropie/configs/all/retroarch.cfg.rp-dist

    You could test with default settings by backing up your original retroarch.cfg and then copy retroarch.cfg.rp-dist to retroarch.cfg.

  • USB Audio on the fly switching

    Help and Support
    2
    0 Votes
    2 Posts
    847 Views
    R

    @Raverrevolution

    Did you find a solution for your problem?
    I got nearly the same issue: My retropie is built into a controller-case which can be "docked" to a monitor-cabinet with usb audio.
    But if I take the controller (including the pi) out of the dock, I want it to play all the sounds over hdmi.

    greets bruce

  • 0 Votes
    3 Posts
    3k Views
    S

    Thanks for the reply suprjami. Unfortunately I couldn't get it to work looking at those two links. My knowledge of linux just isn't good enough.

    If only there was a way to use a conditional statement within asound.conf that checks to see if the USB headset is plugged in before changing the default output to it.

  • 0 Votes
    13 Posts
    7k Views
    P

    @Laserdisc
    Hi

    On the Pimoroni forum there have been several people with this type of issue and the fix was to re-solder the existing audio jack socket.

    Cheers

    Paul